Why do we need this? It's not like we're going to be using smithy based endpoints rule traits right?

Ah, this was from copying the pattern used in our codegen-workshop.
I will refactor the build script to use our existing pattern from smoke-test gen

Smithy actually needs all the above dependencies, in the current set up we are not accepting any unknown traits

nit: validate that

for (cont auto& pageIter: paginator) {
  ...
}

works as that is the most idomatic way people will likely use this

make this static/immtuable list, we dont want to re-create this everytime we call the function, this list will never change at runtime

Okay I made it immutable with final and initialized in the constructor, this way we only re-create this once per service generation and not once per trait generation
private final List<TokenResolver> resolvers; initialized in the constructor

premature returning is anti patter lets make this a a stream

resolvers.stream()
                .filter(resolver -> resolver.canResolve(token, op))
                .findFirst()
                .ifPresentOrElse(resolver -> resolver.writeLogic(writer, token, op),
                        () -> {
                            // Fallback
                            if (ShapeUtil.hasTopLevelMember(context.getModel(), op, "IsTruncated")) {
                                writer.write("        return result.GetIsTruncated();");
                            } else {
                                writer.write("        return false;");
                            }
                        });

potentially refactoring the fallback method to a private function

Made it into a stream instead of early return.
Not sure if we need to refactor it to a private function though, its only used in this specific case.